The UX component is an ideal choice for web and mobile application due to its versatility, including the wide range of controls for displaying and editing your data as well as it's ability to integrate with multiple data sources.

Just like standard UX Components controls (such as Textbox, Textarea, RadioButton, etc), the List control is bound to a UX component variable. When the value in any control changes the UX component is considered to be 'dirty'. So for example, if you open a UX and then select a row in a List, ghe UX will go from 'clean' to 'dirty'.

Properties and methods availble for interacting with components and controls in a UX Component

Over 40 videos describing how to create, manipulate, and improve a UX component.

Updates the argument values in the child UX component and refreshes the data shown in List controls and other controls that are based on data Series. Also causes the embedded UX component's 'onSynchronizeDialog' (client-side) and 'onSynchronize' (server-side) events to fire.

This property is optional. Specify a placeholder for where global UX component validation errors should be shown. If you don't specify a value, a default location will be used. If your component uses Panels, then it is recommended that you specify a placeholder here; otherwise any error messages will be shown in a pop-up window. If you do not want the error messages to shown in a pop-up window specify ]]> as the value for the placeholder.

Most of the Javascript controls on a UX component support the concept of 'sub-themes'. This topic discusses how user-defined sub-themes can be added to a UX component.

Current location information can be used in several actions in Action Javascript. These actions include Ajax Callbacks, Centering a Map, Placing a Marker on a Map, Filtering a List for Records within the Vicinity of the Current Location.

This example shows how to create a simple pie chart with a Static data series.